Standarize gateway API asset deployment #74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
The current logic for gateway API is meant to automatically provision the gateway pod , this is sometimes not optimal since turns out that this gateway deployment cannot be tuned due to operator reconciles.
So the idea of this PR is:
--gs-nw
--gw-lb
--gw-class
Also, it uses the gatewayv1 rather than gatewayv1beta of the client
With these changes a execution of a benchmark in a cluster with a running gateway pod in the openshift-ingress namespace and a gatewayclass would be:
Related Tickets & Documents